User interfaces for presenting indications of incoming calls

ABSTRACT

In some embodiments, an electronic device displays an incoming call user interface in response to receiving an indication of an incoming call. In some embodiments, the incoming call user interface is displayed overlaid on a respective user interface that is optionally associated with an application other than the application associated with the incoming call.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.63/041,776, filed Jun. 19, 2020, and U.S. Provisional Application No.63/131,094, filed Dec. 28, 2020, the entire disclosures of which areincorporated herein by reference in their entireties for all purposes.

FIELD OF THE DISCLOSURE

This specification relates generally to electronic devices that displayuser interfaces in response to receiving an indication of an incomingcall (e.g., phone call, video call, etc.), and user interactions withsuch devices.

BACKGROUND

User interaction with electronic devices has increased significantly inrecent years. These devices can be devices such as computers, tabletcomputers, televisions, multimedia devices, mobile devices, and thelike. In some circumstances, users wish to make and receive calls (e.g.,phone calls, voice calls, video calls, etc.) using electronic devices.An electronic device can present a user interface indicating an incomingcall in response to receiving an indication of the incoming call.

SUMMARY

Some embodiments described in this disclosure are directed to ways ofdisplaying a user interface that indicates an incoming call in responseto an indication of an incoming call received at the electronic device.Enhancing these interactions improves the user's experience with thedevice and decreases user interaction time, which is particularlyimportant where input devices are battery-operated.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Detailed Description below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6GG illustrate exemplary ways in which an electronic devicedisplays a user interface in response to an indication of an incomingcall in accordance with some embodiments.

FIGS. 7A-7K is a flow diagram illustrating a method of displaying a userinterface in response to an indication of an incoming call in accordancewith some embodiments of the disclosure.

DETAILED DESCRIPTION Description of Embodiments

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

In some implementations, an example electronic device presents a userinterface in response to receiving an indication of an incoming call(e.g., a phone call, an internet-based voice call, a video call, etc.).Such techniques can reduce the cognitive burden on a user who uses anexample electronic device and provide an indication of the contact oruser account from which the call was made while, in some embodiments,continuing to display a respective user interface of anotherapplication. Further, these techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some embodiments,input controller(s) 160 are, optionally, coupled to any (or none) of thefollowing: a keyboard, an infrared port, a USB port, and a pointerdevice such as a mouse. The one or more buttons (e.g., 208, FIG. 2)optionally include an up/down button for volume control of speaker 111and/or microphone 113. The one or more buttons optionally include a pushbutton (e.g., 206, FIG. 2). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with one or more input devices.In some embodiments, the one or more input devices include atouch-sensitive surface (e.g., a trackpad, as part of a touch-sensitivedisplay). In some embodiments, the one or more input devices include oneor more camera sensors (e.g., one or more optical sensors 164 and/or oneor more depth camera sensors 175), such as for tracking a user'sgestures (e.g., hand gestures) as input. In some embodiments, the one ormore input devices are integrated with the computer system. In someembodiments, the one or more input devices are separate from thecomputer system.

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including process 700 (FIG.7). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

In addition, in methods described herein where one or more steps arecontingent upon one or more conditions having been met, it should beunderstood that the described method can be repeated in multiplerepetitions so that over the course of the repetitions all of theconditions upon which steps in the method are contingent have been metin different repetitions of the method. For example, if a methodrequires performing a first step if a condition is satisfied, and asecond step if the condition is not satisfied, then a person of ordinaryskill would appreciate that the claimed steps are repeated until thecondition has been both satisfied and not satisfied, in no particularorder. Thus, a method described with one or more steps that arecontingent upon one or more conditions having been met could berewritten as a method that is repeated until each of the conditionsdescribed in the method has been met. This, however, is not required ofsystem or computer readable medium claims where the system or computerreadable medium contains instructions for performing the contingentoperations based on the satisfaction of the corresponding one or moreconditions and thus is capable of determining whether the contingencyhas or has not been satisfied without explicitly repeating steps of amethod until all of the conditions upon which steps in the method arecontingent have been met. A person having ordinary skill in the artwould also understand that, similar to a method with contingent steps, asystem or computer readable storage medium can repeat the steps of amethod as many times as are needed to ensure that all of the contingentsteps have been performed.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

User Interfaces and Associated Processes Incoming Call User Interfaces

Users interact with electronic devices in many different manners,including using electronic devices to make and receive calls (e.g.,phone calls, internet-based voice calls, video calls, etc.). Theembodiments described below provide ways in which an electronic devicedisplays user interfaces in response to receiving an indication of anincoming call. Displaying an incoming call user interface enhancesinteractions with a device, thus reducing the amount of time a userneeds to interact with the electronic device while the incoming call isbeing received and reducing the power usage of the device, whichincreases battery life for battery-powered devices. It is understoodthat people use devices. When a person uses a device, that person isoptionally referred to as a user of the device.

FIGS. 6A-6GG illustrate exemplary ways in which an electronic devicedisplays a user interface in response to an indication of an incomingcall in accordance with some embodiments. The embodiments in thesefigures are used to illustrate the processes described below, includingthe processes described with reference to FIGS. 7A-7K. Although FIGS.6A-6GG illustrate various examples of ways an electronic device is ableto perform the processes described below with reference to FIGS. 7A-7K,it should be understood that these examples are not meant to belimiting, and the electronic device is able to perform one or moreprocesses described below with reference to FIGS. 7A-7K in ways notexpressly described below with reference to FIGS. 6A-6GG.

Some of the user interfaces illustrated herein (e.g., in FIGS. 6A-6F and60-6GG) are shown as being presented on a first electronic device 500 a,which may be a media player, smartphone, etc. Some of the user interfaceillustrated herein (e.g., in FIGS. 6G-6N) are shown as being presentedon a second electronic device 500 b, which may be a tablet. It should beunderstood that, in some embodiments, any of the user interfacesillustrated in FIGS. 6A-6GG are displayed on any electronic device, suchas a media player, smartphone, tablet, computer (e.g., laptop or desktopcomputer), wearable device (e.g., smart watch), or another electronicdevice not expressly listed here.

In some embodiments, in response to receiving an indication of anincoming call, the electronic device 500 a displays an incoming calluser interface overlaid on another user interface displayed by theelectronic device 500 a. FIGS. 6A-6B illustrate an example of theelectronic device 500 a receiving an incoming call while displaying amessaging user interface and, in response to the indication of theincoming call, displaying the incoming call user interface overlaid onthe messaging user interface. It should be appreciated that theelectronic device 500 a is able to display the incoming call userinterface overlaid on user interfaces other than messaging userinterfaces, such as system user interfaces of the electronic device 500a and/or user interfaces associated with applications other than themessaging application.

FIG. 6A illustrates the electronic device 500 a displaying an exemplarymessaging user interface. The messaging user interface illustrated inFIG. 6A includes representations 602 a-c of messages in the messagingconversation, including a representation 602 a of a message from a userother than the user of the electronic device 500 a and representations602 b and 602 c of messages from the user of the electronic device 500a. The messaging user interface further includes a text entry field 604toward which one or more inputs for composing a message are directed, anoption 606 to send a message (e.g., to send content entered into textentry field 604 as a message to the messaging conversation), and a softkeyboard 608 which is optionally one of one or more ways of enteringcontent into text entry field 604. The electronic device 500 a alsodisplays an indication 605 a of the current time, an indication 605 b ofa network connection (e.g., a wireless network connection, such as aWi-Fi connection) of the electronic device 500 a, and an indication 605c of the current battery life of the electronic device 500 a. In someembodiments, the electronic device 500 a displays the indications 605a-c while displaying user interfaces other than the messaging userinterface.

In FIG. 6B, the electronic device 500 a detects an indication 607 b ofan incoming call. The incoming call is optionally a phone call, though,in some embodiments, the incoming call is an internet-based voice call,a video call, or another form of real-time communication. As shown inFIG. 6B, in response to detecting the indication 607 b of the incomingcall, the electronic device 500 a displays an incoming call userinterface 610 a overlaid on the messaging user interface. The incomingcall user interface 610 a includes an indication 618 a of the user fromwhich the call was received, an indication 620 a of the device orservice from which the call was received, an image 612 a associated withthe user from which the call was received, a selectable option 614 athat, when selected, causes the electronic device 500 a to decline thecall, and a selectable option 616 a that, when selected, causes theelectronic device 500 a to accept the call.

In some embodiments, the indication 618 a of the user from which thecall is received, the indication 620 a of the device or service fromwhich the call was received, and the image 612 a associated with theuser from which the call is received include data included in a contactcard of the user from which the call is received. For example, theelectronic device 500 a detects a phone number from which the incomingcall is received and matches it to the phone number stored as the“smartphone” associated with the contact “Mom” and displays the name 618a of the contact, the device 620 a from which the call was received, andthe image 612 a associated with the contact card in the incoming calluser interface 610 a. In some embodiments, if the incoming call isreceived from a user account that is not a contact of the electronicdevice 500 a, instead of displaying the name 618 a of the contact, theelectronic device 500 a displays an indication of the user account(e.g., the phone number from which the call was received, the usernamefrom which an internet-based phone call or video call is received) fromwhich the call was received, displays a generic image instead of animage 612 a associated with the user account, and/or displays anindication of the service through which the call was received instead ofdisplaying the indication 620 a of the device from which the call wasreceived.

In some embodiments, while the indication 607 b of the incoming call isdetected, the electronic device 500 a continues to display the incomingcall user interface 610 a when a user input directed to a user interfaceother than the incoming call user interface 610 a is received andperforms an action corresponding to the input in response to the input.As shown in FIG. 6B, the user swipes (e.g., with contact 603 b) themessaging user interface to scroll the messaging user interface. Asshown in FIG. 6C, in response to the user input illustrated in FIG. 6B,the electronic device 500 a scrolls the messaging user interface whilecontinuing to display the incoming call user interface 610 a. Thus,FIGS. 6B-6C illustrate an example of the electronic device 500 aperforming an action in response to a user input while continuing todisplay the incoming call user interface 610 a. In some embodiments, theuser input is a user input to show or hide a user interface other thanthe incoming call user interface 610 a. For example, if the electronicdevice 500 a were to detect a user input corresponding to a request tocease displaying the messaging user interface, the electronic device 500a would, in response to the input, cease displaying the messaging userinterface while continuing to display the incoming call user interface610 a. As another example, in response to an input corresponding to arequest to display a user interface of a respective application otherthan the messaging application (e.g., selection of an icon correspondingto a respective application displayed in a home screen user interface),the electronic device 500 a would display the user interface of therespective application and continue to display the incoming call userinterface 610 a.

In some embodiments, the electronic device 500 a displays an expandedcall user interface in response to an input directed to the incomingcall user interface 610 a. As shown in FIG. 6C, the user selects (e.g.,with contact 603 c) the incoming call user interface 610 a and moves thecontact 603 c down. In response to the input illustrated in FIG. 6C, theelectronic device 500 a displays the expanded incoming call userinterface illustrated in FIG. 6D, 6E, or 6F.

FIG. 6D illustrates an exemplary incoming call user interface. Theexpanded incoming call user interface is displayed in response to theuser input illustrated in FIG. 6C. As shown in FIG. 6D, the expandedincoming call user interface includes the name 618 b of the contact fromwhich the incoming call is received, an indication 620 b of theelectronic device 500 from which the call is received, an image 612 bassociated with the contact from which the call is received, an option622 a to set a reminder to call the user back, an option 624 a toinitiate a process to send a message to the user, an option 614 b toreject the incoming call, and an option 616 b to accept the incomingcall. Thus, the expanded incoming call user interface includes options622 a and 624 a that were not included in the incoming call userinterface illustrated in FIGS. 6B and 6C. As shown in FIG. 6D, theexpanded call user interface occupies the area of display 504 a in whichthe messaging user interface was previously displayed in FIG. 6C.

FIG. 6E illustrates another exemplary expanded incoming call userinterface. The expanded incoming call user interface is displayed inresponse to the user input illustrated in FIG. 6C. As shown in FIG. 6E,the expanded incoming call user interface includes the name 618 c of thecontact from which the incoming call is received, an indication 620 c ofthe electronic device 500 from which the call is received, an image 612c associated with the contact from which the call is received, an option622 c to set a reminder to call the user back, an option 624 c toinitiate a process to send a message to the user, an option 614 c toreject the incoming call, and an option 616 c to accept the incomingcall. Thus, the expanded incoming call user interface includes options622 c and 624 c that were not included in the incoming call userinterface illustrated in FIGS. 6B and 6C. As shown in FIG. 6E, theexpanded call user interface is overlaid on a portion of the messaginguser interface that is larger than the portion of the messaging userinterface over which the incoming call user interface 610 a illustratedin FIGS. 6B-6C was displayed.

FIG. 6F illustrates another exemplary expanded incoming call userinterface. The expanded incoming call user interface is displayed inresponse to the user input illustrated in FIG. 6C. As shown in FIG. 6F,the expanded incoming call user interface includes the name 618 d of thecontact from which the incoming call is received, an indication 620 d ofthe electronic device 500 from which the call is received, an image 612d associated with the contact from which the call is received, an option622 d to set a reminder to call the user back, an option 624 d toinitiate a process to send a message to the user, an option 614 d toreject the incoming call, and an option 616 d to accept the incomingcall. Thus, the expanded incoming call user interface includes options622 d and 624 c that were not included in the incoming call userinterface illustrated in FIGS. 6B and 6C. As shown in FIG. 6F, theexpanded call user interface is overlaid on a portion of the messaginguser interface that is larger than the portion of the messaging userinterface over which the incoming call user interface 610 a illustratedin FIGS. 6B-6C was displayed.

In some embodiments, an electronic device 500 b displays the userinterface of a first application in a respective region of the display504 b area that is partially overlaid on the user interface of a secondapplication. The electronic device 500 b is able to display the incomingcall user interface within the respective region of the display 504 barea, as will now be described in more detail below with reference toFIGS. 6G-6N.

FIG. 6G illustrates the electronic device 500 b displaying a webbrowsing user interface in a respective region 638 of the display 504 barea overlaid on a messaging user interface. As shown in FIG. 6G, theweb browsing user interface includes an address bar 640 and the contentof a website 642. The respective region 638 includes a first userinterface element 644 a towards which an input to cease displaying therespective region 638 of the user interface is directed and a seconduser interface element 644 b toward which an input to toggle the userinterface displayed in respective region 638 is directed. The messaginguser interface includes a search bar 626 toward which a user inputsearching the contents of messages is directed, an option 628 that, whenselected, causes the electronic device 500 b to initiate a process tocompose a new message, representations 634 a-e of messagingconversations, including a representation 634 b of a messagingconversation that is currently displayed, a text entry field 636 towardwhich input to add contents to a message is directed, and a plurality ofrepresentations of messages including representation 602 g included inthe messaging conversation corresponding to representation 634 b.

In FIG. 6H, the electronic device 500 b detects an indication 607 i ofan incoming call. In response to detecting the indication 607 i, theelectronic device 500 b displays an incoming call user interface 610 cin the respective region 638 of the display 504 b area. The incomingcall user interface 610 c can include elements similar to the elementsof incoming call user interface 610 a described above with reference toFIG. 6B. In some embodiments, the incoming call user interface 610 a isdisplayed at the location illustrated in FIG. 6H even when theelectronic device 500 b is not displaying another user interface (e.g.,the web browsing user interface) in the respective region 638 at thetime at which the indication 607 i of the incoming call is received.

In FIG. 6I, the user selects (e.g., with contact 603 i) the incomingcall user interface 610 c and moves contact 603 i down in a mannersimilar to the manner in which the user interacts with the incoming calluser interface 610 a in FIG. 6C. As shown in FIG. 6J, in response to theinput illustrated in FIG. 6I, the electronic device 500 b ceasesdisplaying the web browsing user interface in the respective region 638of the display 504 b area and displays an expanded incoming call userinterface in the respective region 638 of the display 504 b area.

FIG. 6J illustrates the electronic device 500 b displaying the expandedincoming call user interface in the respective region 638 of the display504 b area. The expanded incoming call user interface is displayed inthe respective region 638 of the display 504 b area in response to theuser input illustrated in FIG. 6I. As shown in FIG. 6J, the expandedincoming call user interface includes the name 618 e of the contact fromwhich the incoming call is received, an indication 620 e of theelectronic device 500 from which the call is received, an image 612 eassociated with the contact from which the call is received, an option622 e to set a reminder to call the user back, an option 624 e toinitiate a process to send a message to the user, an option 614 e toreject the incoming call, and an option 616 e to accept the incomingcall. Thus, the expanded incoming call user interface includes options622 e and 624 e that were not included in the incoming call userinterface illustrated in FIGS. 6H and 6I.

In FIG. 6K, the user selects (e.g., with contact 603 k) the second userinterface element 644 b and moves the contact 603 k horizontally in aswipe motion. In FIG. 6L, in response to the input illustrated in FIG.6K, the electronic device 500 b ceases displaying the incoming call userinterface in the respective region 638 of the display 504 b area anddisplays the web browsing user interface in the respective region 638 ofthe display 504 b area again. In some embodiments, if the user were toperform the input illustrated in FIG. 6K again, the electronic device500 b would toggle through a plurality of user interfaces previouslydisplayed in the respective region 638 of the display 504 b area. Asshown in FIG. 6L, while the indication 607 j of the incoming callcontinues to be detected and the expanded incoming call user interfaceis no longer displayed, the electronic device 500 b displays anindication 646 a of the incoming call in region of the display 504 bthat includes indications 604 a-c. In some embodiments, indication 646 ais animated, as described in more detail below with reference to FIGS.6V-6W. In some embodiments, instead of displaying indication 646 a, theelectronic device 500 b displays an indication similar to indication 646c described in more detail below with reference to FIG. 6Z. In someembodiments, in response to detecting selection of indication 646 a, theelectronic device 500 b displays the expanded incoming call userinterface illustrated in FIG. 6M or the incoming call user interface 610c illustrated in FIG. 6I.

In FIG. 6L, the user selects (e.g., with contact 603 l) the second userinterface element 644 b and moves the contact 603 l in a directionopposite to the direction in which the user moved contact 603 k in FIG.6K to perform a swipe input. In FIG. 6M, in response to the user inputillustrated in FIG. 6M, the electronic device 500 b ceases displayingthe indication 646 a and displays the expanded incoming call userinterface in the respective region 638 of the display 504 b, as shown inFIG. 6M.

In FIG. 6M, the user selects (e.g., with contact 603 m) the first userinterface element and moves the contact 603 m towards an edge of thedisplay 504 b that is closest to the respective region 638 of thedisplay 504 b. In FIG. 6N, in response to the input illustrated in FIG.6M, the electronic device 500 b ceases displaying a user interface otherthan the messaging user interface in the respective region 638 of thedisplay 504 b area and displays the indication 646 a. Indication 646 ais described in more detail above with reference to FIG. 6L.

In some embodiments, the electronic device 500 a (or 500 b) displays anongoing call user interface in response to detecting an inputcorresponding to a request to accept an incoming call while the call isongoing. FIG. 6O illustrates an exemplary user input corresponding to arequest to accept an incoming call. As shown in FIG. 6O, in response toan indication 607 o of an incoming call, the electronic device 500 adisplays the incoming call user interface 610 a described above withreference to FIGS. 6B-6C. The user selects (e.g., with contact 603 o)the selectable option 616 a to accept the incoming call. In response tothe user's selection, the electronic device 500 a accepts the incomingcall and connects the electronic device 500 a to the electronic devicefrom which the call was received to initiate a two-way real-timecommunication channel through which the electronic devices are able tocommunicate and updates the user interface as illustrated in FIG. 6P.

FIG. 6P illustrates an exemplary ongoing call user interface 610 f. Insome embodiments, the user interface illustrated in FIG. 6P is displayedin response to the input illustrated in FIG. 6O. The ongoing call userinterface 610 f is displayed in the same region of the display as theincoming call user interface 610 illustrated in FIG. 6O. The ongoingcall user interface includes an indication 618 f of the user the call iswith, an image 612 f corresponding to the user the call is with, anindication 620 f of the elapsed time since the call was accepted, aselectable option 614 f to terminate the call, and an option 616 f toview one or more audio settings of the audio of the call.

In FIG. 6Q, the user selects (e.g., with contact 603 q) the option 616 fto view the audio settings associated with the audio of the call, asshown in FIG. 6R. FIG. 6R illustrates a plurality of selectable options648 a-c displayed in response to the input illustrated in FIG. 6Q.Option 648 c is displayed with a checkmark to indicate that the audio ofthe call is currently being presented through a headset in communicationwith the electronic device 500 a. In response to detecting selection ofone of the other options 648 a or 648 b, the electronic device 500 aoptionally ceases presenting the call audio through the headset andpresents the call audio through the selected other audio device incommunication with the electronic device 500 a, such as a phone speakerintegrated with the electronic device 500 a (which, in this example, isa smartphone) associated with option 648 a or a loudspeaker deviceintegrated with electronic device 500 a associated with option 648 b.

As described above with reference to FIGS. 6B-6C, in some embodiments,while the electronic device 500 a displays the incoming call userinterface 610 a, in response to receiving an input directed to a userinterface other than the incoming call user interface 610 a, theelectronic device 500 a performs the action in accordance with the inputand continues to display the incoming call user interface 610 a. Incontrast, in some embodiments, while the electronic device 500 a isdisplaying the ongoing call user interface 610 f, in response toreceiving an input directed to a user interface other than the ongoingcall user interface 610 f, the electronic device 500 a performs theaction in accordance with the input and ceases displaying the ongoingcall user interface 610 f, as will be described below with reference toFIGS. 6S-6T.

In FIG. 6S, the electronic device 500 a displays the ongoing call userinterface 610 f overlaid on the messaging user interface. Whiledisplaying the ongoing call user interface 610 f overlaid on themessaging user interface, the user makes a selection (e.g., with contact603 s) within the messaging user interface and moves contact 603 s toscroll the messaging user interface.

As shown in FIG. 6T, in response to the input illustrated in FIG. 6S,the electronic device 500 a scrolls the user interface in accordancewith the input, ceases displaying the ongoing call user interface 610 f,and displays an indication 646 d of the ongoing call. The indication 646d of the ongoing call includes or is displayed with the indication 605 aof the current time. For example, the indication 646 d of the ongoingcall is an indication that is a different color than the backgroundcolor on which indications 605 b and 605 c are displayed. Although FIG.6T illustrates indication 646 d as having a pattern, in someembodiments, the indication 646 d is a solid color. In some embodiments,in response to detecting selection of indication 646 d, the electronicdevice 500 a displays either the ongoing call user interface 610 fillustrated in FIG. 6S or a full-screen, expanded ongoing call userinterface that includes the same elements as the ongoing call userinterface 610 f and additional elements (e.g., one or more indicationsand/or options) not included in the ongoing call user interface 610 f.

In some embodiments, the electronic device 500 a displays an indicationof an incoming call in the same location at which the indication 646 dof the ongoing call was displayed, as shown in FIG. 6T. The indicationof the incoming call can be different from the indication of the ongoingcall, as will be described with reference to FIGS. 6V-6W.

In some embodiments, the indication of the incoming call is displayed inresponse to an input directed to the incoming call user interface 610 a.In FIG. 6U, the electronic device 500 a displays the incoming call useinterface 610 a overlaid on the messaging user interface in response tothe indication 607 u of an incoming call. While displaying the incomingcall user interface 610 a overlaid on the messaging user interface, theelectronic device 500 a detects selection (e.g., with contact 603 u) ofthe incoming call user interface 610 a and movement of the contact 603 utowards the edge of display 504 a closest to the incoming call userinterface 610 a.

As shown in FIG. 6V, in response to the user input illustrated in FIG.6U, the electronic device 500 a ceases displaying the incoming call userinterface 610 a and displays an indication 646 b of the incoming call.The electronic device 500 a forgoes accepting or rejecting the incomingcall and the indication 607 u of the incoming call continues to bedetected. The indication 646 b of the incoming call is displayed at alocation in the user interface at which the indication of the time 605 awas previously displayed while the electronic device 500 a displayed theincoming call user interface 610 a, as shown in FIG. 6U. This locationis also the location at which the indication 646 d of the ongoing callwas displayed while the electronic device 500 a was on a call, as shownin FIG. 6T.

The indication 646 b of the incoming call and the indication 646 d ofthe ongoing call may differ in multiple ways. In some embodiments, theindication 646 b of the incoming call and the indication 646 d of theongoing call include different colored backgrounds. The indication 646 dof the ongoing call includes the indication 605 a of the current time(or the current time 605 a is overlaid on the indication 646 d), whereasthe indication 605 a of the current time is not displayed concurrentlywith the indication 646 b of the incoming call. The indication 646 d ofthe ongoing call is optionally not animated, whereas the indication 646b of the ongoing call is animated, as described with reference to FIGS.6V-6W. In some embodiments, the indication 646 d of the ongoing call isselectable to display a user interface associated with the ongoing call,whereas the indication 645 b of the incoming call is selectable todisplay a user interface associated with the incoming call, as will bedescribed below with reference to FIGS. 6W-6Y.

FIGS. 6V-6W illustrate multiple frames of the animation included in theindication 646 b of the incoming call. In FIG. 6W, the electronic device500 a detects selection (e.g., via contact 603 w) of the indication 646b of the incoming call. In some embodiments, in response to the inputillustrated in FIG. 6W, the electronic device 500 a displays theincoming call user interface 610 a as shown in FIG. 6X. The incomingcall user interface 610 a illustrated in FIG. 6X is described in moredetail above with reference to FIG. 6B. In some embodiments, in responseto the input illustrated in FIG. 6W, the electronic device 500 adisplays the expanded incoming call user interface, as shown in FIG. 6Y.The expanded incoming call user interface illustrated in FIG. 6Y isdescribed in more detail above with reference to FIG. 6D. In someembodiments, in response to the input illustrated in FIG. 6W, theelectronic device 500 a displays the expanded call user interfaceillustrated in FIG. 6E. In some embodiments, in response to the inputillustrated in FIG. 6W, the electronic device 500 a displays theexpanded call user interface illustrated in FIG. 6F.

In some embodiments, instead of displaying the indication 646 b of theincoming call illustrated in FIGS. 6V-6W, the electronic device 500 adisplays the indication 646 c of the incoming call illustrated in FIG.6Z. As shown in FIG. 6Z, the indication 646 c of the incoming callincludes the image 612 g associated with the user from which theincoming call is received. In some embodiments, in response to detectingselection of indication 646 c, the electronic device 500 a displays theincoming call user interface 610 a or an expanded incoming call userinterface, in a manner similar to the manner in which the electronicdevice 500 a displays the incoming call user interface 610 a or anexpanded incoming call user interface in response to detecting selectionof the indication 646 b of the incoming call user interface illustratedin FIG. 6W, as described in more detail above. In some embodiments, oneor more other details of indication 646 b described above apply toindication 646 c illustrated in FIG. 6Z.

In some embodiments, the electronic device 500 a presents an indication(e.g., including a visual indication) of a notification event inresponse to detecting the notification event. Examples of notificationevents include receipt of messages, indications generated by one or moreapplications installed on the electronic device, indications generatedby an operating system of the electronic device 500 a, and the like. Insome embodiments, the electronic device 500 a forgoes presenting anindication of a notification event while an incoming call user interface610 a is displayed in response to an incoming call.

FIG. 6AA illustrates the electronic device 500 a displaying the incomingcall user interface 610 a overlaid on the messaging user interface inresponse to an indication 607 y of an incoming call. While displayingthe incoming call user interface 610 a, the electronic device 500 adetects a notification event 650. As shown in FIG. 6AA, the electronicdevice 500 a forgoes presenting an indication of the notification event650 because the incoming call user interface 610 a is being displayed.In some embodiments, the indication 607 y of the incoming call ispresented for a threshold 654 amount of time before a voicemail systemof the electronic device 500 a accepts the incoming call, allowing thecaller to leave a voicemail. In FIG. 6AA, a respective amount of time652 a has passed since receiving the indication 607 y of the incomingcall and the respective amount of time 652 a is less than the threshold654 time, so the call user interface 610 a continues to be displayed andthe electronic device 500 a continues to forgo presenting an indicationof the notification event 650.

In FIG. 6BB, once the time 652 b since the indication 607 y of theincoming call illustrated in FIG. 6AA reaches the predeterminedthreshold 654 amount of time, the electronic device 500 a no longerreceives the indication 607 y of the incoming call and a voicemailsystem of the electronic device 500 a optionally accepts the incomingcall. Because the incoming call user interface 610 a is no longerdisplayed, the electronic device 500 a presents a visual indication 656of the notification event 650 illustrated in FIG. 6AA. In someembodiments, the electronic device 500 a also presents an audio and/ortactile indication in conjunction with the visual indication 656 of thenotification event.

In some embodiments, if the user had accepted the incoming callcorresponding to the incoming call user interface 610 a illustrated inFIG. 6AA, the electronic device 500 a would present the indication 656of the notification and accepted the call in response to the inputcorresponding to a request to accept the incoming call. For example, theelectronic device 500 a would present the visual indication 656 of thenotification event above or below the ongoing call user interface (e.g.,ongoing call user interface 610 f illustrated in FIG. 6P).

In some embodiments, instead of displaying indication 646 b illustratedin FIGS. 6V-6W in response to the user input illustrated in FIG. 6Uwithout accepting or rejecting the incoming call, the electronic device500 a rejects the incoming call in response to detecting the inputillustrated in FIG. 6U. FIG. 6CC illustrates the electronic device 500 adetecting selection (e.g., with contact 603 cc of the incoming call userinterface 610 a) followed by movement of contact 603 cc towards the edgeof display 504 a closest to the incoming call user interface 610 a, asdescribed above with respect to FIG. 6U. In FIG. 6DD, in response to theinput illustrated in FIG. 6CC, the electronic device 500 a declines theincoming call and presents an indication 658 that the incoming call wasdeclined. In some embodiments, declining the incoming call causes avoicemail system of the electronic device 500 a to answer the call andforgoes initiating a real-time communication channel with the electronicdevice from which the incoming call was received. As shown in FIG. 6DD,the visual indication 658 of the declined call includes the image 612 gassociated with the user from which the incoming call was received andan icon 660 indicating that the call was declined. In some embodiments,the indication 658 is displayed for a predetermined time until theelectronic device 500 a ceases displaying indication 658 without a userinput to do so. In some embodiments, the indication 658 is displayeduntil a user input directed to the indication 658 is received or until auser input not directed to the indication 648 is received.

In some embodiments, the incoming call is a video call. One or more ofthe examples described above apply to phone calls, video calls,internet-based voice calls, or other types of calls. In someembodiments, the electronic device 500 a presents a preview of the videothat will be sent to the other electronic device during a video callbefore the video call is initiated, as will be described below withreference to FIGS. 6EE-6GG. In some embodiments, the video preview iscaptured by a camera in communication with or integrated with electronicdevice 500 a.

FIG. 6EE illustrates the electronic device 500 a presenting anindication 610 h of an incoming video call in response to receiving anindication 607 cc of the incoming video call. The incoming call userinterface 610 h includes elements similar to the elements of theincoming call user interface described above with reference to FIG. 6B,for example, with differences that will now be described. The incomingcall user interface 610 h includes an indication 620 h that the incomingcall is a video call in place of the indication 620 a of the device fromwhich the call is received. In some embodiments, the background of theincoming call user interface 610 h is a video preview indicating thevideo that will be transmitted to the other electronic device if thecall is accepted. In some embodiments, however, the incoming call userinterface 610 h does not include the video preview 662. For example, thebackground of the incoming call user interface 610 h is a solid color.As shown in FIG. 6EE, the electronic device 500 a detects selection(e.g., with contact 603 ee) of an option 616 h to accept the video call.In some embodiments, in response to the input illustrated in FIG. 6EE,the electronic device 500 a accepts the video call. In some embodiments,in response to the input illustrated in FIG. 6EE, the electronic device500 a displays one of the expanded incoming call user interfacesillustrated in FIGS. 6FF and 6GG.

FIG. 6FF illustrates an expanded incoming call user interface that, insome embodiments, is displayed in response to the user input illustratedin FIG. 6EE. The expanded incoming call user interface illustrated inFIG. 6FF is similar to the expanded incoming call user interfacedescribed above with reference to FIG. 6D, for example, except for thedifferences that will now be described. The background of the expandedincoming call user interface in FIG. 6FF includes a video preview 664 ofthe video that will be sent to the other electronic device when thevideo call is accepted and the option 616 j to accept the video callincludes an indication of an amount of time remaining before the videocall will be initiated without further user input. In some embodiments,once the predetermined time (e.g., 1, 2, 3 or 4 or 5 seconds) has passed(e.g., either since the indication of the incoming call was firstreceived or since the input illustrated in FIG. 6EE was received), theelectronic device 500 a initiates the video call automatically in theabsence of a user input corresponding to a request to initiate the videocall. In some embodiments, if the electronic device 500 a detectsselection of the option 616 j to accept the video call before thepredetermined time has passed, the electronic device 500 a initiates thevideo call in response to the input.

FIG. 6GG illustrates an expanded incoming call user interface that, insome embodiments, is displayed in response to the user input illustratedin FIG. 6EE. The expanded call user interface is similar to the expandedcall user interface illustrated in FIG. 6GG, except for the differencesthat will now be described. Instead of displaying an indication of apredetermined time before the video call will automatically beinitiated, the electronic device 500 a displays an option 616 k toaccept the video call that does not include an indication of a countdownto the predetermined time passing and only initiates the video call inresponse to detecting selection of option 616 k.

FIGS. 7A-7K is a flow diagram illustrating a method of displaying a userinterface in response to an indication of an incoming call in accordancewith some embodiments of the disclosure. The method 700 is optionallyperformed at an electronic device such as device 100, device 300, device500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B and5A-5H. Some operations in method 700 are, optionally combined and/ororder of some operations is, optionally, changed.

In some embodiments, method 700 is performed at an electronic device incommunication with a display generation component and one or more inputdevices (e.g., a mobile device (e.g., a tablet, a smartphone, a mediaplayer), a computer (e.g., a desktop computer, a laptop computer), or awearable device (e.g., a watch, a head-mounted device)). In someembodiments, the display generation component is a display integratedwith the electronic device (optionally a touch screen display) and/or anexternal display such as a monitor, projector, television, etc.

In some embodiments, while displaying, via the display generationcomponent, a respective user interface, the electronic device (e.g.,500) detects (702) an indication (e.g., 607 b) of an incoming call atthe electronic device (e.g., 500), such as in FIG. 6B. In someembodiments, the respective user interface that is displayed while theindication of the incoming call is received is the respective userinterface for an application accessible to the electronic device or asystem user interface of the electronic device (e.g., a home screen userinterface). For example, a home screen user interface is a userinterface that includes a plurality of icons and/or widgets or otherapplication content associated with applications accessible to theelectronic device that, when selected, causes the electronic device(e.g., 500) to present a user interface of the correspondingapplication. In some embodiments, the home screen user interface furtherincludes one or more widgets of one or more applications, such as clock,calendar, weather, e-mail, or other widgets. In some embodiments, awidget is a user interface element associated with an application thatincludes a subset of features, functionality and/or information includedin a full user interface of the application. In some embodiments, theindication of the incoming call is received while the electronic deviceis displaying a user interface of an application accessible to theelectronic device. For example, the respective user interface includesuser interface elements with which the user is able to interact to useone or more features of the application. An exemplary home screen userinterface according to some embodiments is described above withreference to FIG. 4A. The respective user interface is optionally not auser interface of a phone application on the electronic device. In someembodiments, the incoming call is received by the electronic device(e.g., the incoming call is detected by cellular telephone circuitry,cellular data circuitry, or other network communication circuitry of theelectronic device). For example, a smartphone receives a phone call madeto a cell phone number of a cellular identifier (e.g., a SIM card oreSIM) of the smartphone. In some embodiments, the indication of theincoming call is received from another electronic device associated witha user account of the electronic device. For example, a tablet that isin communication with a smart phone receives, from the smartphone, anindication of a phone call made to a cell phone number of a cellularidentifier (e.g., a SIM card or eSIM) of the smartphone. In thisexample, the tablet and smartphone are in communication via a wirelessnetwork, such as Bluetooth and/or Wi-Fi and the tablet is able to sendand receive data associated with the telephone call to and from thesmartphone, enabling the user to use the tablet as an interface toconduct the phone call.

In some embodiments, such as in FIG. 6B, in response to detecting theindication (e.g., 607 b) of the incoming call at the electronic device(e.g., 500), the electronic device (e.g., 500) displays 704, overlaid onthe respective user interface, a call user interface (e.g., 610 a) thatincludes a selectable option (e.g., 616 a) for accepting the incomingcall. In some embodiments, the call user interface is a banner displayedat a predetermined location on the display screen at which otherindications of notifications are optionally displayed by the electronicdevice (e.g., at the top portion of the respective user interface). Insome embodiments, the call user interface includes an indication of acontact or user account from which the phone call is received, aselectable option that, when selected, causes the electronic device toaccept the incoming call and connect the electronic device to the callerto conduct the phone call, and a selectable option that, when selected,causes the electronic device to reject the phone call and initiate aprocess to terminate the connection between the caller and theelectronic device.

In some embodiments, while displaying the call user interface (e.g., 610a) overlaid on the respective user interface, the electronic device(e.g., 500) receives (706), via the one or more input devices, an inputdirected to the call user interface (e.g., 610 a), such as in FIG. 6C.

In some embodiments, in response to receiving the input directed to thecall user interface (708), in accordance with a determination that theinput comprises selection of the selectable option (e.g., 616 a) in thecall user interface, the electronic device (e.g., 500) accepts (710) theincoming call, such as in FIGS. 60-6P. In some embodiments, acceptingthe incoming call includes initiating a process to connect theelectronic device to an electronic device of the caller and initiate aphone call between the two devices. In some embodiments, in response toselection of the selectable option to accept the call, the electronicdevice updates the call user interface to include an option that, whenselected, causes the electronic device to display one or more audiosettings of the call (e.g., a plurality of options associated withvarious speakers or audio-generating devices in communication with theelectronic device that, when selected, causes the electronic device touse the selected speaker to play the audio of the call.).

In some embodiments, in response to receiving the input directed to thecall user interface (708), in accordance with a determination that theinput comprises an input directed to the call user interface (e.g., 610a) that includes movement in a first direction (e.g., a swipe input or atouch and drag input), the electronic device (e.g., 500) a displays(712), via the display generation component, an expanded call userinterface, different from the call user interface (e.g., 610 a), whereinthe expanded call user interface includes information associated withthe incoming call that is not included in the call user interface, suchas in FIGS. 6C-6D. In some embodiments, the electronic device ceasesdisplaying the respective user interface over which the call userinterface was previously overlaid to display the expanded call userinterface. In some embodiments, the expanded call user interfaceincludes one or more user interface elements that were included in thecall user interface, such as selectable options to accept the call andreject the phone call (e.g., initiate a process to terminate theconnection between the electronic device and the electronic device ofthe caller). In some embodiments, the expanded call user interfaceincludes user interface elements that were not included in the call userinterface, such as a selectable option to set a reminder to call thecaller back and a selectable option to initiate a process to send a textmessage or enhanced data-based message to the caller. The swipe input isoptionally an input in a first direction (e.g., a downward swipe). Insome embodiments, in response to a swipe input in the opposite direction(e.g., an upward swipe) the electronic device ceases display of the calluser interface, forgoes displaying the expanded call user interface,presents a different visual indication of the incoming call (e.g., anindication in a header region of the respective user interface), forgoesaccepting the phone call, and/or forgoes rejecting the phone call.

The above-described manner of displaying the expanded call userinterface in response to the swipe input enables the electronic deviceto preserve display area for the respective user interface displayedconcurrently with the call user interface unless and until the userrequests to view that expanded call user interface by providing theswipe input, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by maintainingthe context of the respective user interface and forgoing interruptingthe user's interactions with the respective user interface displayedconcurrently with the call user interface, thus avoiding extra inputsfor the user to dismiss an expanded call user interface in order tocomplete their interactions with the respective user interface that wasdisplayed when the call came into the device), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, in response to receiving the input directed to thecall user interface (714), in accordance with the determination that theinput comprises selection of the selectable option (e.g., 616 a) in thecall user interface (e.g., the selectable option that, when selected,causes the electronic device to accept the call), the electronic device(e.g., 500) accepts (716) the incoming call and maintains display of thecall user interface (e.g., 610 f) overlaid on the respective userinterface, such as in FIGS. 6O-6P. In some embodiments, accepting thecall includes initiating a connection with the electronic device fromwhich the incoming call was received to establish a real-time audioand/or video communication channel with the electronic device from whichthe incoming call was received. In some embodiments, the electronicdevice continues to display the respective user interface that wasdisplayed before the indication of the incoming call was received inresponse to detecting selection of the option to accept the call. Forexample, if the electronic device was displaying a user interface of afirst application when the indication of the incoming call was received,the electronic device displays the call user interface overlaid on therespective user interface of the first application in response to theindication of the incoming call and continues to display the call userinterface overlaid on the respective user interface of the firstapplication and accepts the call in response to detecting selection ofthe option to accept the call. As another example, if the electronicdevice was displaying a user interface of a second application when theindication of the incoming call was received, the electronic devicedisplays the call user interface overlaid on the respective userinterface of the second application in response to the indication of theincoming call and continues to display the call user interface overlaidon the respective user interface of the second application and acceptsthe call in response to detecting selection of the option to accept thecall. As another example, if the electronic device was displaying asystem user interface when the indication of the incoming call wasreceived, the electronic device displays the call user interfaceoverlaid on the system user interface in response to the indication ofthe incoming call and continues to display the call user interfaceoverlaid on the system user interface and accepts the call in responseto detecting selection of the option to accept the call.

The above-described manner of maintaining display of the call userinterface overlaid on the respective user interface enables theelectronic device to provide an efficient way of displaying therespective user interface while the call is in progress, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by continuing to display therespective user interface after the call is answered without a userinput to do so), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, in response to receiving the input directed to thecall user interface (718), in accordance with the determination that theinput comprises an input directed to the call user interface 710 a thatincludes movement in the first direction (e.g., a swipe input or a touchand drag input), display (720) the expanded call user interface withoutaccepting the incoming call, such as in FIGS. 6C-6D. In someembodiments, the expanded call user interface will continue to bedisplayed until the indication of the incoming call ceases (e.g., thecall goes to voicemail or the caller terminates the call) if an input toaccept the call is not received. In some embodiments, in response todetecting selection of an option to accept the call that is included inthe expanded call user interface, the electronic device accepts the calland continues to display the expanded call user interface. In someembodiments, in response to receiving an input accepting the call whiledisplaying the expanded call user interface, the electronic deviceupdates the expanded call user interface to include an indication of theduration of the call.

The above-described manner of displaying the expanded call userinterface without accepting the incoming call provides a quick andefficient manner of providing additional information and/or optionsrelated to the incoming call before the call is accepted, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by presenting theinformation and options associated with the incoming call withoutaccepting the call unless and until an input to accept the call isreceived), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, in response to receiving the input directed to thecall user interface (722), in accordance with the determination that theinput comprises selection of the selectable option (e.g., 616 a) in thecall user interface (e.g., selection of the option to accept the call),the electronic device (e.g., 500) updates (724) the call user interfaceto include one or more selectable options (e.g., 616 f) for controllingone or more audio options (e.g., an option to select an audio outputdevice through which to play the audio of the call, an option to raiseor lower the volume of the audio of the call) associated with the call,such as in FIGS. 6O-6P. In some embodiments, the electronic devicedisplays an audio option at the location in the respective userinterface at which the option to accept the incoming call had beendisplayed prior to receiving the input to accept the incoming call. Inresponse to detecting selection of the audio option, the electronicdevice displays a plurality of options associated with audio outputdevices in communication with the electronic device that, when selected,causes the electronic device to play the audio of the call through theselected audio output device. For example, the audio options include anoption to play the audio through one or more speakers integrated withthe electronic device and/or an option to play the audio through aconnected headset or Bluetooth device.

The above-described manner of displaying the one or more selectableoptions for controlling one or more audio options associated with thecall in the call user interface provides a quick and efficient manner ofchanging an audio option associated with the call while continuing todisplay the call user interface overlaid on the respective userinterface, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by reducingthe inputs needed to change an audio option while continuing to view therespective user interface), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6C, the call user interface (e.g.,610) is displayed (726) overlaid on a first portion of the respectiveuser interface (e.g., at or near a top edge of the respective userinterface), and the first direction of the movement is from the firstportion of the respective user interface towards a second portion of therespective user interface (e.g., up, down, to the right, or to theleft), opposite the first portion. In some embodiments, the movement isfrom the call user interface towards the respective user interface onwhich the call user interface is overlaid. For example, the call userinterface is displayed along the top edge of the respective userinterface and, in response to a swipe or select and drag input downward,the electronic device displays the expanded calling user interface(e.g., and ceases displaying the respective user interface).

The above-described manner of displaying the call user interfaceoverlaid on a first edge of the respective user interface and displayingthe expanded call user interface in response to an input including amovement away from the first edge of the respective user interfaceprovides an efficient and intuitive way to display the expanded calluser interface, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byreducing the number of inputs and the amount of time it takes to displaythe expanded call user interface), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6D, the expanded call userinterface includes (728) one or more selectable options (e.g., 622 a)and (e.g., 624 a) for controlling one or more operations associated withthe call, wherein the one or more selectable options (e.g., 622 a) and(e.g., 624 a) were not included in the call user interface (e.g., 610 a)that was displayed prior to detecting the input directed to the calluser interface, such as in FIG. 6C. In some embodiments, the expandedcall user interface includes an option to send a message to the callerof the incoming call and an option to set a reminder associated with theincoming call (e.g., a reminder to call the caller back)—in someembodiments, these options were not displayed in the call userinterface, and are displayed in the expanded call user interface. Insome embodiments, both the call user interface and the expanded calluser interface include options to accept the call and to decline thecall.

The above-described manner of displaying selectable options in theexpanded call user interface that were not included in the call userinterface enables the electronic device to preserve display area whiledisplaying the call user interface overlaid on the respective userinterface by forgoing displaying some of the options unless and untilreceiving an input to display the expanded call user interface, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by maintaining the contextof the respective user interface and forgoing interrupting the user'sinteractions with the respective user interface displayed concurrentlywith the call user interface, thus avoiding extra inputs for the user todismiss an expanded call user interface in order to complete theirinteractions with the respective user interface that was displayed whenthe call came into the device), which additionally reduces power usageand improves battery life of the electronic device by enabling the userto use the electronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6D, the expanded call userinterface is displayed (730) without displaying the respective userinterface on which the call user interface (e.g., 610 a) was overlaidprior to detecting the input directed to the call user interface, suchas in FIG. 6C (e.g., in a full screen mode via the display generationcomponent). In some embodiments, in response to the input to display theexpanded call user interface, the electronic device ceases displayingthe respective user interface and displays the expanded call userinterface at the location at which the respective user interface hadbeen displayed. For example, in response to receiving the user input todisplay the expanded call user interface while displaying the respectiveuser interface in a full screen mode, the electronic device ceasesdisplaying the respective user interface and displays the expanded calluser interface in a full screen mode. In some embodiments, theelectronic device displays a second user interface in a first respectiveregion concurrently with the respective user interface in a secondrespective region, and the call user interface when the input to displaythe expanded call user interface is received. In some embodiments, inresponse to receiving the input to display the expanded call userinterface, the electronic device ceases displaying the respective userinterface in the second respective region and displays the expanded calluser interface in the second respective region while continuing todisplay the second user interface in the first respective region.

The above-described manner of displaying the expanded call userinterface without displaying the respective user interface enables theelectronic device to allocate enough display area to the expanded calluser interface to display expanded information and options associatedwith the incoming call, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by providing the information and options associated with theincoming call in an efficient manner), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6H, the respective user interfaceis a user interface of a first application (e.g., the first applicationis an application other than the application through which the call isreceived (e.g., a phone application, a virtual or internet phoneapplication, a voice chat application, etc.). In some embodiments, therespective user interface is a system user interface of the operatingsystem of the electronic device.

In some embodiments, such as in FIG. 6J, the expanded call userinterface is displayed (734) overlaid on the respective user interfacein a respective region (e.g., 638) of a display area of the displaygeneration component (e.g., 504 b), the respective region (e.g., 638)configured to display one or more user interfaces of one or more secondapplications overlaid on the respective user interface of the firstapplication. In some embodiments, the electronic device is configured todisplay one or more user interfaces in a first region of the displayarea while displaying another user interface in a second region overlaidon the first region. In some embodiments, the second region is smallerthan the first region so that the respective user interface displayed inthe first region (e.g., the respective user interface of the firstapplication) is partially visible while the respective user interface(e.g., of the one or more second applications) is displayed in thesecond region overlaid on the first region. In some embodiments, therespective user interface of the first application occupies the entiredisplay area other than the respective region. In some embodiments, therespective user interface of the first application occupies a portion(e.g., half, a third, etc.) of the full screen display region other thanthe respective region. For example, the electronic device displays therespective user interface of the first application and a user interfaceof a third application such that these user interfaces together occupythe first region of the display area. In some embodiments, theindication of the incoming call is received while the electronic devicedisplays a user interface of a second application in the respectiveregion of the respective user interface (e.g., overlaid over therespective user interface of the first application) and, in response tothe indication of the incoming call, the electronic device reduces thesize of the respective user interface of the second application todisplay both the respective user interface of the second application andthe call user interface in the respective region of the display area(e.g., overlaid on the respective user interface of the firstapplication). In some embodiments, in response to receiving the inputincluding movement in the first direction while displaying the call userinterface and the respective user interface of the second application,the electronic device ceases displaying the respective user interface ofthe second application and displays the expanded call user interface inthe respective region (e.g., overlaid on the respective user interfaceof the first application). In some embodiments, the electronic device isnot displaying a user interface of a second application in therespective region when the indication of the incoming call is receivedand, in response to receiving the indication of the incoming call, theelectronic device displays the call user interface in the respectiveregion (e.g., overlaid on the respective user interface of the firstapplication). In some embodiments, the call user interface is displayedat a size that is smaller than the maximum size of the respective region(e.g., the size at which the respective user interface of the secondapplication is displayed in the respective region) unless and until theinput including movement in the first direction is received. In someembodiments, in response to receiving the input including movement inthe first direction while displaying the call user interface in therespective region without displaying a user interface of a secondapplication in the respective region, the electronic device displays theexpanded call user interface in the respective region (e.g., overlaid onthe respective user interface of the first application).

The above-described manner of displaying the call user interface in therespective region enables the electronic device to continue displayingthe respective user interface of the first application while displayingthe call user interface in a manner similar to other user interfacesoverlaid on the first user interface, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by maintaining the context of the respective userinterface and forgoing interrupting the user's interactions with therespective user interface displayed concurrently with the call userinterface, thus avoiding extra inputs for the user to dismiss anexpanded call user interface in order to complete their interactionswith the respective user interface that was displayed when the call cameinto the device), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6K, while displaying the expandedcall user interface in the respective region (e.g., 638) overlaid on therespective user interface, the electronic device (e.g., 500) receives(736), via the one or more input devices, a second input directed to theexpanded call user interface (e.g., a movement corresponding to arequest to change the respective user interface displayed in therespective region). In some embodiments, in response to receiving thesecond input directed to the expanded call user interface (738), inaccordance with a determination that the second input comprises an inputdirected to a first region of the expanded call user interface thatincludes movement in a second direction (740) (e.g., a swipe or touchand drag or select and drag input to the left or right), the electronicdevice (e.g., 500) ceases (742) display of the expanded call userinterface in the respective region (e.g., 638), such as in FIG. 6L. Insome embodiments, the input is directed to a portion and/or userinterface element in the expanded call user interface at a bottom edgeof the expanded call user interface element.

In some embodiments, the electronic device (e.g., 500) displays (744),in the respective region (e.g., 638), a respective user interface of asecond application overlaid on the respective user interface of thefirst application, such as in FIG. 6L. In some embodiments, therespective user interface of the second application had been previouslydisplayed in the respective region before the incoming call wasreceived. For example, while the electronic device is displaying thecall user interface in the respective region, the electronic devicereceives an input to change the respective user interface displayed inthe respective region and in response to the input, the electronicdevice ceases displaying the call user interface and displays a userinterface for the second application. In some embodiments, in responseto the input and while ceasing to display the call user interface, theelectronic device displays an indication of the incoming and/or acceptedcall at a predetermined location in the display area of the displaygeneration component other than the respective region (e.g., in a headerregion in which information such as the current time, the connectivitystatus of the electronic device, and other information is displayed).

The above-described manner of displaying the respective user interfaceof the second application in the respective region in response to theinput provides an intuitive and efficient way of ceasing to display thecall user interface in the respective region that is similar to the waythe electronic device ceases displaying other user interfaces displayedin the respective region, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by reducing the time it takes to display the respective userinterface of the second application compared to waiting until theincoming call is no longer received before ceasing to display the calluser interface), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, in response to receiving the second input directedto the expanded call user interface (746), in accordance with adetermination that the second input comprises an input directed to asecond region of the expanded call user interface that includes movementin a third direction (748) (e.g., a swipe, touch and drag, or select anddrag movement up), such as in FIG. 6M, the electronic device (e.g., 500)ceases (750) display of the expanded call user interface in therespective region (e.g., 638) without displaying, in the respectiveregion, the respective user interface of the second application overlaidon the respective user interface of the first application, such as inFIG. 6N (e.g., and without displaying any other user interface overlaidon the respective user interface of the first application). In someembodiments, the third direction is different from the second direction.In some embodiments, the third direction is the same as the seconddirection. In some embodiments, the input is directed to a portionand/or user interface element in the expanded call user interface at atop edge of the expanded call user interface element. In someembodiments, in response to the second input and ceasing displaying theexpanded call user interface, the electronic device displays anindication of the incoming and/or accepted call in a region of therespective user interface other than the respective region. For example,the visual indication is displayed in a header region in whichinformation, such as the current time and the network connection statusof the electronic device are displayed.

The above-described manner of ceasing display of the expanded call userinterface without displaying a user interface of the second applicationoverlaid on the respective user interface of the first applicationprovides a quick and efficient way to resume displaying the respectiveuser interface of the first application in an unobstructed way, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by allowing the user tocontinue viewing the respective user interface of the first applicationwhile the indication of the incoming call is still being received),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, such as in FIG. 6E, the expanded call userinterface is overlaid on a first portion (e.g., less than the entirety)of the respective user interface while maintaining display of a secondportion of the respective user interface (e.g., without being overlaidon a second portion of the respective user interface), the call userinterface is overlaid on a third portion of the respective userinterface, smaller than the first portion, and the first portion of therespective user interface is smaller than an entirety of the respectiveuser interface (752). In some embodiments, the call user interface isdisplayed at a size smaller than the expanded call user interface and atleast a portion of the respective user interface is stillvisible/displayed while the expanded call user interface is beingdisplayed. In some embodiments, in response to detecting an inputselecting a region of the expanded call user interface that is not aselectable option, the electronic device expands the expanded call userinterface to a full screen size.

The above-described manner of displaying the expanded call userinterface on a first portion of the respective user interface enablesthe electronic device to continue displaying a portion of the respectiveuser interface concurrently with the expanded call user interface, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by reducing the time ittakes to resume viewing the respective user interface after viewing theexpanded call user interface, maintaining the context of the respectiveuser interface, avoiding interrupting the user's interactions with therespective user interface, and reducing the inputs needed to resumeinteracting with the respective user interface), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, such as in FIG. 6EE, in accordance with adetermination that the incoming call comprises a video call, the calluser interface (e.g., 610 h) includes a preview (e.g., 662) of videogenerated by the electronic device that will be used in the video callif the video call is accepted (754). In some embodiments, the video iscaptured by a camera in communication with the electronic device, suchas a camera integrated with the electronic device, and captures video ofthe user of the electronic device for use in the video call, ifaccepted. In some embodiments, the call user interface is sizeddifferently than a video calling user interface and once the video callbegins, the aspect ratio and/or field of view of the video changes fromthe aspect ratio and/or field of view of the preview of the video.

The above-described manner of displaying the video preview in the calluser interface provides a quick and efficient way to convey that videowill be transmitted to the caller in response to detecting an input toaccept the video call, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byreducing erroneous inputs to accept video calls that would not haveotherwise been accepted if it were known that the call was a videocall), which additionally reduces power usage and improves battery lifeof the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, while displaying, overlaid on the respective userinterface, a respective call user interface for a respective incomingcall, wherein the respective call user interface (e.g., 610 h) includesa respective selectable option (e.g., 616 h) (e.g., an option that, whenselected, causes the electronic device to initiate a process to acceptthe incoming call), the electronic device (e.g., 500) receives (756),via the one or more input devices, a second input directed to therespective call user interface (e.g., 610 h), such as in FIG. 6EE. Insome embodiments, in response to receiving the second input directed tothe respective call user interface (758), in accordance with adetermination that the second input comprises selection of therespective selectable option (e.g., 616 h) in the respective call userinterface (e.g., 610 h) (760), in accordance with a determination thatthe incoming call is not a video call, the electronic device (e.g., 500)accepts (762) the incoming call, such as in FIG. 6O. In someembodiments, the call is accepted in response to detecting selection ofthe option without any additional input between receipt of selection ofthe option and acceptance of the call. In some embodiments, the call isa telephone call, an internet-based voice call, or other call includingaudio that does not include video. In some embodiments, in accordancewith a determination that the incoming call is a video call, withoutaccepting the video call, the electronic device (e.g., 500) displays(764), via the display generation component, a respective expanded calluser interface that includes video generated by the electronic devicethat will be used in the video call if the video call is accepted, suchas in FIG. 6FF. In some embodiments, the respective call user interfaceincludes an option that, when selected, causes the electronic device toaccept the video call. In some embodiments, in response to accepting thevideo call, the electronic device captures video and transmits the videoto the caller. In some embodiments, the video preview is captured by acamera in communication with the electronic device, such as a cameraintegrated with the electronic device, and captured video of the user ofthe electronic device that will be used in the video call, if accepted.

The above-described manner of displaying the expanded call userinterface without accepting the call when the call is a video callprovides a quick and efficient way to convey that video will betransmitted to the caller in response to detecting an input to acceptthe video call, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byreducing erroneous inputs to accept video calls that would not haveotherwise been accepted if it were known that the call was a videocall), which additionally reduces power usage and improves battery lifeof the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, in response to receiving the input directed to thecall user interface (e.g., detecting selection of an option to acceptthe incoming call) (766), such as in FIG. 6EE, in accordance with adetermination that the incoming call is a video call 768, such as inFIG. 6EE, without accepting the video call, the electronic device (e.g.,500) displays (770), via the display generation component, the expandedcall user interface that includes video (e.g., 664) generated by theelectronic device that will be used in the video call if the video callis accepted, such as in FIG. 6FF. In some embodiments, the background ofthe expanded call user interface includes the video generated by theelectronic device that will be used in the video call if the video callis accepted. In some embodiments, the video is captured by a cameraintegrated with or in communication with the electronic device. In someembodiments, while displaying the respective expanded call userinterface including the video (e.g., 664) generated by the electronicdevice (e.g., 500), in accordance with a determination that an elapsedtime since the respective expanded call user interface was displayedexceeds a time threshold (e.g., 1, 2, 3, 5, or 7 seconds), theelectronic device (e.g., 500) accepts (772) the video call. In someembodiments, the expanded call user interface includes an indication ofthe amount of time before the video call will be accepted. In someembodiments, the expanded call user interface further includes aselectable option that, when selected, causes the electronic device toaccept the video call before the predetermined elapsed time has passed.In some embodiments, in accordance with a determination that theincoming call is not a video call, the electronic device (e.g., 500)accepts (774) the incoming call without displaying the expanded calluser interface, such as in FIG. 6P.

The above-described manner of accepting the video call in accordancewith the determination that the elapsed time has passed since theexpanded call user interface was displayed provides a quick andefficient way to automatically accept the video call once the expandedcall user interface is displayed, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by reducing the number of inputs needed to accept thevideo call), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, such as in FIG. 6GG the respective expanded calluser interface that includes the video (e.g., 666) generated by theelectronic device (e.g., 500) includes a second respective selectableoption (e.g., 616 k) for accepting the video call (776). In someembodiments, while displaying the respective expanded call userinterface, the electronic device 50 receives (778), via the one or moreinput devices, a third input selecting the second respective selectableoption (e.g., 616 k). In some embodiments, in response to receiving thethird input selecting the second respective selectable option, theelectronic device accepts (780) the video call. In some embodiments, theelectronic device automatically captures and sends video to the otherparticipant in the video call in response to the input to accept thevideo call. In some embodiments, the input to accept the call isreceived before the predetermined period of time has passed and theelectronic device initiates the video call before the predetermined timehas passed.

The above-described manner of concurrently displaying a secondrespective selectable option for accepting the video call with the videopreview provides a quick manner of accepting the video call withouthaving to wait for the elapsed time to reach the time threshold, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by reducing the time neededto accept the video call), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, in response to receiving the input directed to thecall user interface (782), in accordance with a determination that theinput comprises an input directed to the call user interface (e.g., 610a) that includes movement in a second direction (e.g., up), differentfrom the first direction (e.g., a swipe input or a touch and draginput), such as in FIG. 6U, the electronic device (e.g., 500) ceases(784) display of the call user interface (e.g., 610 a) and displays, viathe display generation component, a visual indication (e.g., 646 b),different from the call user interface, of the incoming call, such as inFIG. 6V. In some embodiments, for some devices (e.g., devices not havingsensors at the top of the display that occupy display area), a statusbar at the top of the respective user interface changes color and thevisual indication is displayed within the status bar but doesn't replaceexisting content of the status bar. In some embodiments, for somedevices (e.g., devices with sensors at top of display that occupy somedisplay area) the visual indication replaces content (e.g., the currenttime) that was displayed at the top of the respective user interface. Insome embodiments, for some devices (e.g., tablets), the visualindication of the incoming call is displayed next to existing content inthe top region of the respective user interface. In some embodiments, inresponse to the input, an audio and/or other type of indication (e.g.,tactile) of the incoming call (e.g., ringtone) is silenced but call isnot declined. In some embodiments, in response to the input, theelectronic device declines the call. In some embodiments, the visualindication of the incoming call continues to be displayed for theduration during which the indication of the incoming call is detectedand the electronic device ceases displaying the visual indication of theincoming call when the incoming call is disconnected and/or ceases.

The above-described manner of displaying the visual indication of theincoming call in response to the input provides a quick and efficientway of ceasing display of the call user interface but maintaining anindication corresponding to the incoming call, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by reducing the display area needed to indicatethe incoming call, thereby enabling the user to continue viewing thefull user interface), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6W, while displaying the visualindication (e.g., 646 b) of the incoming call, the electronic device(e.g., 500) receives (786), via the one or more input devices, an inputselecting (e.g., via a tap or selection with a cursor, key, or button,etc.) the visual indication (e.g., 646 b) of the incoming call. In someembodiments, in response to receiving the input selecting the visualindication (e.g., 646 b) of the incoming call, the electronic device(e.g., 500) displays (788), via the display generation component, thecall user interface (e.g., 610 a) overlaid on the respective userinterface, such as in FIG. 6X. In some embodiments, in response to theinput and while displaying the call user interface, the electronicdevice ceases displaying the visual indication of the incoming call.

The above-described manner of displaying the call user interface inresponse to selection of the visual indication of the incoming callprovides an efficient way of viewing information about the incoming calland options to accept or decline the call, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by reducing the number of inputs needed to viewthe information about the call compared to navigating to an applicationassociated with the incoming call instead of selecting the indication ofthe incoming call), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, while displaying the visual indication (e.g., 646b) of the incoming call, the electronic device (e.g., 500) receives(790), via the one or more input devices, an input selecting the visualindication (e.g., 646 b) of the incoming call. In some embodiments, inresponse to receiving the input selecting the visual indication (e.g.,646 b) of the incoming call, the electronic device (e.g., 500) displays(792), via the display generation component, the expanded call userinterface, such as in FIG. 6Y. In some embodiments, in response to theinput and while displaying the expanded call user interface, theelectronic device ceases displaying the visual indication of theincoming call.

The above-described manner of displaying the expanded call userinterface in response to selection of the visual indication of theincoming call provides an efficient way of viewing information about theincoming call and options to accept or decline the call, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by reducing the number ofinputs needed to view the information about the call compared tonavigating to an application associated with the incoming call insteadof selecting the indication of the incoming call), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, such as in FIGS. 6V-6W, the visual indication(e.g., 646 b) includes an animation corresponding to the incoming call.In some embodiments, such as in FIG. 6T, after accepting the incomingcall (e.g., while the call is connected and ongoing) and while the calluser interface is not displayed (e.g., and the expanded call userinterface is not displayed, either), the electronic device (e.g., 500)displays (796), via the display generation component, a second visualindication (e.g., 646 d) of the accepted call, wherein the second visualindication (e.g., 646 d) is displayed with a visual characteristichaving a first value that is different from a second value for thevisual characteristic with which the visual indication of the incomingcall is displayed. In some embodiments, the animation includes changingone or more of the colors of the visual indication (e.g., a backgroundcolor, a foreground color, etc.) as the incoming call is pending. Insome embodiments, the animation includes an animated illustration as theincoming call is pending, such as flashing colors, a vibrating orshaking phone icon, etc. In some embodiments, the visual indication ofthe accepted call does not include an animation.

The above-described manner of including an animation in the visualindication of the incoming call efficiently distinguishes the visualindication from the rest of the respective user interface and/or statusvisual indications that might be displayed in its location, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by effectively conveying themeaning of the indication without the need for further user input),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, such as in FIG. 6V, the visual indication (e.g.,646 b) is displayed at a location in the respective user interface atwhich a second visual indication (e.g., 646 d) of a second call isdisplayed while the electronic device (e.g., 500) is participating inthe second call, such as in FIG. 6T (798). In some embodiments, theelectronic device has accepted the second call). In some embodiments,the electronic device displays the visual indication of the incomingcall at the same location as an indication of a call that is inprogress. For example, the electronic device displays the visualindication of the incoming call, receives a sequence of one or moreinputs to accept the call, and then, while the call is occurring,displays a visual indication of the ongoing call at the same location inthe respective user interface at which the visual indication of theincoming call was displayed. In some embodiments, the visual indicationof the incoming call has a different appearance (e.g., color, content,animations, etc.) than the visual indication of the ongoing call.

The above-described manner of displaying the visual indication of theincoming call at the same location at which the electronic devicedisplays the second visual indication of the second call enables theelectronic device to efficiently indicate the status of incoming andongoing calls without using unnecessary display area, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., by displaying the indications of theincoming call and the second call at the same location, the user is ableto more quickly locate the indications), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, such as in FIG. 6Z, the visual indication (e.g.,646 c) includes a representation (e.g., 612 g) of a respective userassociated with the incoming call, other than a user of the electronicdevice (798-2). In some embodiments, a contact card including a nameand/or contact information of the contact that is accessible to theelectronic device includes an image (e.g., avatar, picture, etc.)associated with the contact. In some embodiments, the image associatedwith the contact is included in the visual indication of the incomingcall. In some embodiments, if the incoming call has multipleparticipants, the visual indication of the incoming call includes avisual indication of each (or at least multiple, if not all)participant.

The above-described manner of including the representation of therespective user in the indication of the incoming call efficientlyindicates the user that is making the incoming call, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., by reducing the number of inputs neededto confirm who the call is from while displaying the visual indicationof the incoming call), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, such as in FIG. 6B, while displaying the call userinterface (e.g., 610 a) overlaid on the respective user interface, andbefore accepting the incoming call, the electronic device (e.g., 500)receives (798-4), via the one or more input devices, a first inputinteracting with the respective user interface (e.g., the first inputincludes selection of an element included in the respective userinterface (e.g., selection of an application icon to display theapplication), and/or an input navigating from the first user interfaceto a different user interface other than the call user interface orexpanded call user interface, etc.). In some embodiments, such as inFIG. 6C, in response to receiving the first input interacting with therespective user interface, the electronic device (e.g., 500) updates(798-6) the respective user interface in accordance with the first inputinteracting with the respective user interface while maintaining displayof the call user interface (e.g., 610 a) overlaid on the updatedrespective user interface. In some embodiments, the electronic devicecontinues to display the call user interface overlaid on the displayeduser interface unless and until an input dismissing the call userinterface is received (e.g., an input to display the expanded call userinterface, an input to dismiss the call user interface) or the incomingcall ceases to be received (e.g., the call disconnects or is answered bya voicemail system).

The above-described manner of updating the respective user interface inresponse to the first input while maintaining display of the call userinterface overlaid on the updated user interface reduces the number ofinputs needed to interact with the call user interface after interactingwith the respective user interface while the call user interface isdisplayed, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic device(e.g., by maintaining the context of the respective user interface andforgoing interrupting the user's interactions with the respective userinterface displayed concurrently with the call user interface, thusavoiding extra inputs for the user to dismiss an expanded call userinterface in order to complete their interactions with the respectiveuser interface that was displayed when the call came into the device)and makes the user-device interface more efficient, which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, such as in FIG. 6S, while displaying the call userinterface (e.g., 610 f) overlaid on the respective user interface andafter the incoming call has been accepted (e.g., while the electronicdevice is participating in the call), the electronic device (e.g., 500)receives (798-8), via the one or more input devices, a second inputinteracting with the respective user interface. In some embodiments, thesecond input includes selection of an element included in the respectiveuser interface (e.g., selection of an application icon to display theapplication), and/or an input navigating from the first user interfaceto a different user interface other than the call user interface orexpanded call user interface, etc. In some embodiments, in response toreceiving the second input interacting with the respective userinterface, the electronic device (e.g., 500) cease (798-10) display ofthe call user interface and updating the respective user interface inaccordance with the second input interacting with the respective userinterface, such as in FIG. 6T. In some embodiments, once the call hasbeen accepted, in response to a user input directed to a user interfaceother than the call user interface, the electronic device ceasesdisplaying the call user interface and performs the action associatedwith the input. For example, in response to receiving an input selectingan option in the respective user interface while displaying the calluser interface overlaid on the respective user interface, the electronicdevice performs the action associated with the option (e.g., navigatesto another user interface, such as a user interface of anotherapplication) and ceases displaying the call user interface overlaid onthe respective user interface. In some embodiments, in response todetecting a user input directed to the call user interface, theelectronic device performs the action in accordance with the input andcontinues displaying the call user interface overlaid on the respectiveuser interface. For example, in response to detecting selection of anoption to view one or more audio settings of the call included in thecall user interface, the electronic device displays the audio optionsand continues displaying the call user interface.

The above-described manner of ceasing display of the call user interfaceand updating the respective user interface in accordance with the secondinput while the call is in progress provides an efficient way of ceasingdisplay of the call user interface when input to the call user interfaceis less likely, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byreducing the number of inputs needed to view the respective userinterface unobstructed while the call is in progress), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, while displaying the call user interface overlaidon the respective user interface and before accepting the incoming call(798-12), the electronic device (e.g., 500) detects (798-14) anotification event (e.g., 650) at the electronic device (e.g., 500),such as in FIG. 6AA. In some embodiments, the notification event is anevent that causes the electronic device to present an indication (e.g.,a visual, audio, or tactile indication) of the event. For example, thenotification event is one of an incoming message, an upcoming calendarappointment, or an application alert. In some embodiments, in responseto detecting the notification event (e.g., 650) at the electronicdevice, the electronic device (e.g., 500) delays (798-16) presentation(e.g., display) of a respective (e.g., visual, audio, tactile)indication (e.g., 656) of the notification event, such as in FIGS.6AA-6BB. In some embodiments, the electronic device forgoes presentingthe indication (e.g., visual indication, audio indication, tactileindication) of the alert while the incoming call is being received. Theelectronic device optionally presents the indication after delayingpresentation of the respective indication of the notification event inresponse to a subsequent event at the device that is related to thenotification event such as ceasing to detect the incoming call and/orceasing to display the call user interface, such as because the call wasdeclined, accepted, disconnected by the caller, or answered by avoicemail system, or because the device otherwise detected an input todismiss the call user interface. The above-described manner of delayingdisplay of the respective indication while the indication of theincoming call is being detected enables the electronic device to avoidaltering display of the call user interface while the call is incoming,and thus avoiding erroneous input interaction with the call userinterface or the respective user interface more generally while the callis incoming, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by reducingthe chance of user error caused by trying to select one user interfaceelement and accidentally selecting a different user interface element),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, after delaying the presentation of the respectivevisual indication of the notification event, in accordance with adetermination that the incoming call has been accepted, the electronicdevice (e.g., 500) presents (798-18) the respective indication of thenotification event. In some embodiments, the electronic device continuesto display the call user interface while displaying the visualindication of the notification event. In some embodiments, the visualindication of the notification event is displayed at the location in therespective user interface at which the call user interface had beendisplayed and the electronic device moves the location of the call userinterface (e.g., downward). In some embodiments, the electronic devicemaintains the location of the call user interface on the display anddisplays the indication of the notification at a different location inthe respective user interface, such as below the call user interface. Insome embodiments, the electronic device concurrently presents the visualindication of the notification event with a tactile or audio indicationof the notification event.

The above-described manner of presenting the visual indication of thenotification event after the call is accepted enables the electronicdevice to promptly inform the user of the notification event, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by reducing the time ittakes the user to act on the notification event), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, in response to receiving the input directed to thecall user interface (e.g., 610 a) (798-20), such as in FIG. 6CC, inaccordance with a determination that the input comprises an inputdirected to the call user interface that includes movement in a seconddirection, different from the first direction (798-22) (e.g., a swipeinput or a touch and drag input up), the electronic device (e.g., 500)ceases (798-24) display of the call user interface, such as in FIG. 6DD.In some embodiments, the electronic device continues to display therespective user interface on which the call user interface had beenoverlaid. In some embodiments, the electronic device (e.g., 500) rejects(798-26) the incoming call, such as in FIG. 6DD. In some embodiments,the electronic device (e.g., 500) displays (798-28), via the displaygeneration component, a visual indication (e.g., 658), different fromthe call user interface, that the incoming call was rejected, such as inFIG. 6DD. In some embodiments, the visual indication is displayed at alocation in the respective user interface at which the call userinterface was previously displayed, and is displayed for a predeterminedtime period (e.g., 1, 2 or 3 seconds) and then ceases to be displayedwithout any user input.

The above-described manner of rejecting the incoming call and displayingthe visual indication that the incoming call was rejected in response tothe input provides an efficient way of rejecting the call and confirmingthat the call was rejected, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by reducing the inputs needed to reject the call), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 7A-7K have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., a as described with respect to FIGS. 1A-1B, 3, 5A-5H)or application specific chips. Further, the operations described abovewith reference to FIGS. 7A-7K are, optionally, implemented by componentsdepicted in FIGS. 1A-1B. For example, displaying operations 704, 712,and 718, presenting operation 798-18, and receiving operations 706, 736,and 756 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch screen 504, and event dispatcher module174 delivers the event information to application 136-1. A respectiveevent recognizer 180 of application 136-1 compares the event informationto respective event definitions 186, and determines whether a firstcontact at a first location on the touch screen corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

As described above, one aspect of the present technology is thegathering and use of data available from specific and legitimate sourcesto present content of relevance to the user. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used toidentify a specific person. Such personal information data can includedemographic data, location-based data, online identifiers, telephonenumbers, e-mail addresses, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, detecting video and/or audio can facilitate useof the electronic device for the purpose of voice and/or video calls.Accordingly, use of such personal information data enables users tocommunicate with other electronic devices. Further, other uses forpersonal information data that benefit the user are also contemplated bythe present disclosure.

The present disclosure contemplates that those entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities would beexpected to implement and consistently apply privacy practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. Such informationregarding the use of personal data should be prominent and easilyaccessible by users, and should be updated as the collection and/or useof data changes. Personal information from users should be collected forlegitimate uses only. Further, such collection/sharing should occur onlyafter receiving the consent of the users or other legitimate basisspecified in applicable law. Additionally, such entities should considertaking any needed steps for safeguarding and securing access to suchpersonal information data and ensuring that others with access to thepersonal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations that may serve to imposea higher standard. For instance, in the US, collection of or access tocertain health data may be governed by federal and/or state laws, suchas the Health Insurance Portability and Accountability Act (HIPAA);whereas health data in other countries may be subject to otherregulations and policies and should be handled accordingly.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, the presenttechnology can be configured to allow users to select to “opt in” or“opt out” of participation in the collection of personal informationdata during registration for services or anytime thereafter. Forexample, users can disable a video calling function of the electronicdevice if they do not wish for video to be captured and transmitted toother electronic devices in this way.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing identifiers, controlling the amount orspecificity of data stored (e.g., collecting location data at city levelrather than at an address level), controlling how data is stored (e.g.,aggregating data across users), and/or other methods such asdifferential privacy.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, phone call andother audio calling functions are operational even if the user haschosen not to share certain personal information, such as locationservices, health data, device usage history, and the like.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

1. A method comprising: at an electronic device in communication with adisplay generation component and one or more input devices: whiledisplaying, via the display generation component, a respective userinterface, detecting an indication of an incoming call at the electronicdevice; in response to detecting the indication of the incoming call atthe electronic device, displaying, overlaid on the respective userinterface, a call user interface that includes a selectable option foraccepting the incoming call; while displaying the call user interfaceoverlaid on the respective user interface, receiving, via the one ormore input devices, an input directed to the call user interface; and inresponse to receiving the input directed to the call user interface: inaccordance with a determination that the input comprises selection ofthe selectable option in the call user interface, accepting the incomingcall; and in accordance with a determination that the input comprises aninput directed to the call user interface that includes movement in afirst direction, displaying, via the display generation component, anexpanded call user interface, different from the call user interface,wherein the expanded call user interface includes information associatedwith the incoming call that is not included in the call user interface.2. The method of claim 1, further comprising: in response to receivingthe input directed to the call user interface: in accordance with thedetermination that the input comprises selection of the selectableoption in the call user interface, accepting the incoming call andmaintaining display of the call user interface overlaid on therespective user interface.
 3. The method of claim 1, further comprising:in response to receiving the input directed to the call user interface:in accordance with the determination that the input comprises an inputdirected to the call user interface that includes movement in the firstdirection, displaying the expanded call user interface without acceptingthe incoming call.
 4. The method of claim 1, further comprising: inresponse to receiving the input directed to the call user interface: inaccordance with the determination that the input comprises selection ofthe selectable option in the call user interface, updating the call userinterface to include one or more selectable options for controlling oneor more audio options associated with the call.
 5. The method of claim1, wherein the call user interface is displayed overlaid on a firstportion of the respective user interface, and the first direction of themovement is from the first portion of the respective user interfacetowards a second portion of the respective user interface, opposite thefirst portion.
 6. The method of claim 1, wherein the expanded call userinterface includes one or more selectable options for controlling one ormore operations associated with the call, wherein the one or moreselectable options were not included in the call user interface that wasdisplayed prior to detecting the input directed to the call userinterface.
 7. The method of claim 1, wherein the expanded call userinterface is displayed without displaying the respective user interfaceon which the call user interface was overlaid prior to detecting theinput directed to the call user interface.
 8. The method of claim 1,wherein: the respective user interface is a user interface of a firstapplication, and the expanded call user interface is displayed overlaidon the respective user interface in a respective region of a displayarea of the display generation component, the respective regionconfigured to display one or more user interfaces of one or more secondapplications overlaid on the respective user interface of the firstapplication.
 9. The method of claim 8, further comprising: whiledisplaying the expanded call user interface in the respective regionoverlaid on the respective user interface, receiving, via the one ormore input devices, a second input directed to the expanded call userinterface; and in response to receiving the second input directed to theexpanded call user interface: in accordance with a determination thatthe second input comprises an input directed to a first region of theexpanded call user interface that includes movement in a seconddirection: ceasing display of the expanded call user interface in therespective region; and displaying, in the respective region, arespective user interface of a second application overlaid on therespective user interface of the first application.
 10. The method ofclaim 9, further comprising: in response to receiving the second inputdirected to the expanded call user interface: in accordance with adetermination that the second input comprises an input directed to asecond region of the expanded call user interface that includes movementin a third direction: ceasing display of the expanded call userinterface in the respective region without displaying, in the respectiveregion, the respective user interface of the second application overlaidon the respective user interface of the first application.
 11. Themethod of claim 1, wherein the expanded call user interface is overlaidon a first portion of the respective user interface while maintainingdisplay of a second portion of the respective user interface, the calluser interface is overlaid on a third portion of the respective userinterface, smaller than the first portion, and the first portion of therespective user interface is smaller than an entirety of the respectiveuser interface.
 12. The method of claim 1, wherein: in accordance with adetermination that the incoming call comprises a video call, the calluser interface includes a preview of video generated by the electronicdevice that will be used in the video call if the video call isaccepted.
 13. The method of claim 1, further comprising: whiledisplaying, overlaid on the respective user interface, a respective calluser interface for a respective incoming call, wherein the respectivecall user interface includes a respective selectable option, receiving,via the one or more input devices, a second input directed to therespective call user interface; and in response to receiving the secondinput directed to the respective call user interface: in accordance witha determination that the second input comprises selection of therespective selectable option in the respective call user interface: inaccordance with a determination that the incoming call is not a videocall, accepting the incoming call; and in accordance with adetermination that the incoming call is a video call, without acceptingthe video call, displaying, via the display generation component, arespective expanded call user interface that includes video generated bythe electronic device that will be used in the video call if the videocall is accepted.
 14. The method of claim 13, wherein the respectiveexpanded call user interface that includes the video generated by theelectronic device includes a second respective selectable option foraccepting the video call, the method further comprising: whiledisplaying the respective expanded call user interface, receiving, viathe one or more input devices, a third input selecting the secondrespective selectable option; and in response to receiving the thirdinput selecting the second respective selectable option, accepting thevideo call.
 15. The method of claim 1, further comprising: in responseto receiving the input directed to the call user interface: inaccordance with a determination that the incoming call is a video call:without accepting the video call, displaying, via the display generationcomponent, the expanded call user interface that includes videogenerated by the electronic device that will be used in the video callif the video call is accepted; and while displaying the respectiveexpanded call user interface including the video generated by theelectronic device, in accordance with a determination that an elapsedtime since the respective expanded call user interface was displayedexceeds a time threshold, accepting the video call; and in accordancewith a determination that the incoming call is not a video call,accepting the incoming call without displaying the expanded call userinterface.
 16. The method of claim 15, wherein the respective expandedcall user interface that includes the video generated by the electronicdevice includes a second respective selectable option for accepting thevideo call, the method further comprising: while displaying therespective expanded call user interface, receiving, via the one or moreinput devices, a third input selecting the second respective selectableoption; and in response to receiving the third input selecting thesecond respective selectable option, accepting the video call.
 17. Themethod of claim 1, further comprising: in response to receiving theinput directed to the call user interface: in accordance with adetermination that the input comprises an input directed to the calluser interface that includes movement in a second direction, differentfrom the first direction, ceasing display of the call user interface anddisplaying, via the display generation component, a visual indication,different from the call user interface, of the incoming call.
 18. Themethod of claim 17, further comprising: while displaying the visualindication of the incoming call, receiving, via the one or more inputdevices, an input selecting the visual indication of the incoming call;and in response to receiving the input selecting the visual indicationof the incoming call, displaying, via the display generation component,the call user interface overlaid on the respective user interface. 19.The method of claim 17, further comprising: while displaying the visualindication of the incoming call, receiving, via the one or more inputdevices, an input selecting the visual indication of the incoming call;and in response to receiving the input selecting the visual indicationof the incoming call, displaying, via the display generation component,the expanded call user interface.
 20. The method of claim 17, whereinthe visual indication includes an animation corresponding to theincoming call, the method further comprising: after accepting theincoming call and while the call user interface is not displayed,displaying, via the display generation component, a second visualindication of the accepted call, wherein the second visual indication isdisplayed with a visual characteristic having a first value that isdifferent from a second value for the visual characteristic with whichthe visual indication of the incoming call is displayed.
 21. The methodof claim 17, wherein the visual indication is displayed at a location inthe respective user interface at which a second visual indication of asecond call is displayed while the electronic device is participating inthe second call.
 22. The method of claim 17, wherein the visualindication includes a representation of a respective user associatedwith the incoming call, other than a user of the electronic device. 23.The method of claim 1, further comprising: while displaying the calluser interface overlaid on the respective user interface, and beforeaccepting the incoming call, receiving, via the one or more inputdevices, a first input interacting with the respective user interface;and in response to receiving the first input interacting with therespective user interface, updating the respective user interface inaccordance with the first input interacting with the respective userinterface while maintaining display of the call user interface overlaidon the updated respective user interface.
 24. The method of claim 23,further comprising: while displaying the call user interface overlaid onthe respective user interface and after the incoming call has beenaccepted, receiving, via the one or more input devices, a second inputinteracting with the respective user interface; and in response toreceiving the second input interacting with the respective userinterface, ceasing display of the call user interface and updating therespective user interface in accordance with the second inputinteracting with the respective user interface.
 25. The method of claim1, further comprising: while displaying the call user interface overlaidon the respective user interface and before accepting the incoming call:detecting a notification event at the electronic device; and in responseto detecting the notification event at the electronic device, delayingpresentation of a respective indication of the notification event. 26.The method of claim 25, further comprising: after delaying thepresentation of the respective visual indication of the notificationevent, in accordance with a determination that the incoming call hasbeen accepted, presenting the respective indication of the notificationevent.
 27. The method of claim 1, further comprising: in response toreceiving the input directed to the call user interface: in accordancewith a determination that the input comprises an input directed to thecall user interface that includes movement in a second direction,different from the first direction: ceasing display of the call userinterface; rejecting the incoming call; and displaying, via the displaygeneration component, a visual indication, different from the call userinterface, that the incoming call was rejected.